-
Notifications
You must be signed in to change notification settings - Fork 154
chore(parser): add parser to release steps #2382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this, looking forward to release this as beta!
If you want to wait to merge it, tomorrow morning I can try running the lerna & pack commands locally and we can use this PR to fix any issue. If instead you have already tested and know it works, merge away! |
You are right, let me first have the dry run tomorrow and then I can merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to also set the "publishConfig"
to "access": "public"
in the package.json
file of the utility, or it won't be published to npmjs.com.
Also we should change the keywords
to something like:
"keywords": [
"aws",
"lambda",
"powertools",
"parser",
"zod",
"parse",
"events",
"payloads",
"inputs",
"validate",
"validation",
"serverless",
"typescript",
"nodejs"
],
I also think we should put back disclaimers on the utility's README and docs page to call out that it's still in beta, that we'd like feedback, and that its API might change. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing the comments - I manually built the package & tested it in a function and basic features seem to work.
I have a couple questions but we can address them in the coming weeks, nothing blocking imo
|
Description of your changes
This PR adds the necessary configurations so we can release
@aws-lambda-powertools/parser
package as a beta in the next release.Related issues, RFCs
Issue number: closes #2366
Checklist
Breaking change checklist
Is it a breaking change?: NO
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.